Update dependency doorkeeper-openid_connect to v1.10.1#11613
Merged
renovate[bot] merged 1 commit intoJun 4, 2026
Conversation
Contributor
Code Coverage Report: Only Changed Files listed
Minimum allowed coverage is |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.10.0→1.10.1Release Notes
doorkeeper-gem/doorkeeper-openid_connect (doorkeeper-openid_connect)
v1.10.1Compare Source
Metrics/ClassLengthandMetrics/BlockLengthoverrides from.rubocop_todo.ymlNaming/VariableNumberfrom.rubocop_todo.ymland normalise test variable names.rubocop_todo.ymland align trailing-comma style with upstream doorkeeperpromptparameter being rejected withinvalid_requestwhen it contains leading or duplicate spaces (e.g.prompt=%20none) — blank entries in the space-delimited value are now ignoredInvalidConfigurationwhen theissuerconfig resolves to a blank value instead of silently advertising an emptyissuerin the discovery document. Since v1.10.0 an arity-2issuerblock receives(resource_owner, application)— bothnilin the discovery context — so a block relying on the old v1.9.0 request argument could returnniland produce a discoveryissuerthat mismatched the ID tokeniss(#298)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.